NCCI-MIB DEFINITIONS::=BEGINIMPORTSMODULE-IDENTITY,OBJECT-TYPE, enterprises
FROM SNMPv2-SMI
TEXTUAL-CONVENTION,RowStatus,TruthValueFROM SNMPv2-TC
ifIndex
FROM IF-MIB
atmVclEntry, atmVplEntry
FROM ATM-MIB
MODULE-COMPLIANCE,OBJECT-GROUPFROM SNMPv2-CONF;atmfNcciMIB MODULE-IDENTITYLAST-UPDATED"0002290000Z"ORGANIZATION"The ATM Forum"CONTACT-INFO"The ATM Forum
2570 West El Camino Real, Suite 304
Mountain View, CA 94040-1313 USA
Phone: +1 415-949-6700
Fax: +1 415-949-6705
info@atmforum.com"DESCRIPTION"The MIB module for managing the ATM Forum
Network Call Correlation Identifier (NCCI) v1.0"REVISION"0002290000Z"DESCRIPTION"Initial version of the MIB module for managing the ATM Forum
Network Call Correlation Identifier v1.0."::={ atmfNcci 1}-- The object identifier subtree for the ATM Forum NCCI MIBsatmForum OBJECTIDENTIFIER::={ enterprises 353}atmForumNetworkManagement OBJECTIDENTIFIER::={ atmForum 5}
atmfSignalling OBJECTIDENTIFIER::={ atmForumNetworkManagement 9}atmfNcci OBJECTIDENTIFIER::={ atmfSignalling 1}ncciMIBObjects OBJECTIDENTIFIER::={ atmfNcciMIB 1}-- ========================================
-- atmNCCIType
-- ========================================AtmNcciType::=TEXTUAL-CONVENTIONSTATUScurrentDESCRIPTION"The network call correlation identifier (NCCI) is used to
uniquely identify a call over ATM networks.
The associated call can be either a point-to-point or
point-to-multipoint call. Both VCCs and VPCs can be
associated with a network call correlation identifier.
A network call correlation identifier (NCCI) can be coded
under two formats : The AESA-based format or the B-ISUP format
The AESA-based NCCI has a length of 28 bytes and is composed
as follows :
- The NCCI root (20 octets) contains the AESA associated
with the entity (node, interface) at which the NCCI is
first assigned to that call.
- The NCCI index (8 octets) is used in combination with the
AESA to provide a NCCI that is unique over a sufficiently
long period of time.
-------------------------------------------------
| NCCI Root (AESA) | NCCI Index |
-------------------------------------------------
The B-ISUP NCCI has a length of 9 bytes and is composed
as follows (defined in ITU Recommendation Q.2726.3) :
- The network identifier (2 octets of 4 BCD digits)
consists of a 0 followed by an E.164 country code
followed by a sufficient number of 0s to make 4 digits.
- The point code (3 octets) contains the SS7 point code
of the node where the NCCI is assigned.
- The Call identifier (4 octets) is used in combination with
the Point Code and the Net ID to provide a NCCI that is
unique over a long period of time.
-----------------------------------------
| Net ID | Point Code | Call Identifier |
-----------------------------------------
"REFERENCE"ATM Forum NCCI v1.0 section 2"SYNTAXINTEGER{none (0),aesaBased(1),bisup(2)}-- ========================================
-- atmNCCI
-- ========================================AtmNcci::=TEXTUAL-CONVENTIONSTATUScurrentDESCRIPTION"Describes the value of a NCCI
Two types of NCCI are defined: the AESA-based and the
B-ISUP formats. These formats are explained in the
AtmNcciType definition.
When the AtmNcciType is equal to none, it means that no
NCCI is contained in the variable. The length of AtmNcci
is equal to zero byte."REFERENCE"ATM Forum NCCI v1.0 section 2"SYNTAXOCTETSTRING(SIZE(0|9|28))
-- ========================================
-- atmNCCIRoot
-- ========================================AtmNcciRoot::=TEXTUAL-CONVENTIONSTATUScurrentDESCRIPTION"The root portion of a NCCI.
Two types of NCCI are defined: the AESA-based and the
B-ISUP formats. These formats are explained in the atmNcciType
definition.
For a NCCI in a AESA-based format, the root portion is equivalent
to the NCCI Root as described in the atmNcciType definition
(20 bytes).
For a NCCI in a B-ISUP format, the root portion is equivalent
to the NCCI Network ID + Point Code as described in the
atmNcciType definition (5 bytes).
When the AtmNcciType is equal to none, it means that no
NCCI is contained in the variable. The length of AtmNcciRoot
is equal to zero byte."REFERENCE"ATM Forum NCCI v1.0 section 2"SYNTAXOCTETSTRING(SIZE(0|5|20))-- ========================================
-- Per Interface NCCI Configuration
-- ========================================ncciIfTable OBJECT-TYPESYNTAXSEQUENCEOF NcciIfEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The table used to manage the assignment of NCCIs on
a per interface basis. One row of this
table can be created by the managed system for each row in
the ifTable of atm(37).
An entry in this table configures the management of NCCIs for
SVCs, SVPs, soft PVCs, and soft PVPs. The configuration can
be applied to point-to-point calls, point-to-multipoint calls
or both.
When no entry in this table has been configured for a given
interface and direction, the action is to forward the received
NCCI if present, and not to assign any NCCI even when no NCCI is
received."REFERENCE"ATM Forum NCCI v1.0"::={ ncciMIBObjects 1}ncciIfEntry OBJECT-TYPESYNTAX NcciIfEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"Each entry in this table is used to configure the NCCI
operations for SETUP messages of svcs and svps.
The entry is also be used to configure the assignment of NCCIs to
soft pvcs or soft pvps whose terminating legs are located on the
interface indexed by ifIndex.
The actions configured in this entry are subject to the procedures
described in sections 3,4 and 5 of the ATM Forum NCCI v1.0.
The ifIndex is used as the instance ID to uniquely identify
the interface on the local switching system. This index has
the same value as the ifIndex object defined in RFC 1573 for
the same interface, since this table correlates with the ifTable
in RFC 1573."INDEX{ ifIndex, ncciIfDirection }::={ ncciIfTable 1}
NcciIfEntry ::=SEQUENCE{
ncciIfDirection INTEGER,
ncciIfAction INTEGER,
ncciIfSave BITS,
ncciIfinConnect TruthValue,
ncciIfType AtmNcciType,
ncciIfRoot AtmNcciRoot,
ncciIfCastType INTEGER,
ncciIfVpType INTEGER,
ncciIfVcType INTEGER,
ncciIfRowStatus RowStatus}ncciIfDirection OBJECT-TYPESYNTAXINTEGER{ incoming (1),outgoing (2)}MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"Indicates if the configuration applies to incoming setup
indications or to outgoing setup requests."::={ ncciIfEntry 1}ncciIfAction OBJECT-TYPESYNTAXINTEGER{discardNcci (1),assignNcci (2),forwardNcci (3)}MAX-ACCESSread-createSTATUScurrentDESCRIPTION"Indicates what action to perform when a setup indication
is received on this interface.
'discardNcci' means that if an incoming setup indication
is received, if a NCCI is present in the setup, it is discarded
and no NCCI is assigned to the call. The values contained
in ncciIfType and ncciIfRoot are ignored.
'assignNcci' means that if an incoming setup indication is
received, a new locally generated NCCI is assigned to the call.
'assignNcci' implies that the ncciIfType is set to a value
different than 'none'.
'forwardNcci' means that if an incoming setup indication
is received, if a NCCI is present in the setup, it is forwarded
to the next interface.
If no NCCI is present:
- a locally generated NCCI is assigned to the call if
the ncciIfType is set to a value different than 'none'.
- no locally generated NCCI is assigned to the call if
the ncciIfType is set to the value 'none'."REFERENCE"ATM Forum NCCI v1.0 sections 3, 4, and 5"DEFVAL{ forwardNcci }::={ ncciIfEntry 2}ncciIfSave OBJECT-TYPESYNTAXBITS{ localNcci (0),remoteNcci (1)}MAX-ACCESSread-createSTATUScurrentDESCRIPTION"Indicates whether NCCIs are saved for calls on this
interface
'localNcci' indicates that the value of
- a newly assigned NCCI, or
- a received NCCI if it has been forwarded, or
- a received NCCI if it has been discarded and either
the atmVclConnKind or the atmVplConnKind is 'svcOutgoing', or
- a received NCCI if the atmVclConnKind or atmVplConnKind
is 'spvcTarget'
is stored.
'remoteNcci' indicates that the value of
- a NCCI received in the SETUP message if either
the atmVclConnKind or the atmVplConnKind is 'svcIncoming', or
- a NCCI received in the CONNECT message if either
the atmVclConnKind or the atmVplConnKind is 'svcOutgoing'
is stored."::={ ncciIfEntry 3}ncciIfinConnect OBJECT-TYPESYNTAXTruthValueMAX-ACCESSread-createSTATUScurrentDESCRIPTION"Indicates whether a locally generated NCCI assigned to an
incoming call on this interface is returned in the
CONNECT message.
'true' means that the NCCI is returned in the CONNECT message.
This object is only applicable on AINI or UNI interfaces
and when ncciIfDirection has the value 'incoming'."DEFVAL{ true }::={ ncciIfEntry 4}ncciIfType OBJECT-TYPESYNTAXAtmNcciTypeMAX-ACCESSread-createSTATUScurrentDESCRIPTION"Indicates the format of the NCCI to be assigned on the
specified interface."REFERENCE
"ATM Forum NCCI v1.0 section 2"DEFVAL{ none }::={ ncciIfEntry 5}ncciIfRoot OBJECT-TYPESYNTAXAtmNcciRootMAX-ACCESSread-createSTATUScurrentDESCRIPTION"Contains the NCCI Root or the NCCI Network ID + Point Code
to be used by the switching system when generating a NCCI
on the specified interface.
If the ncciIfRoot value is not supplied prior to creating the
row, the switching system is in charge of deriving the
ncciIfRoot value from one of the switch addresses.
The value of the NCCI root assigned by the switch can be read
from this variable when the entry in the table has been activated.
The length of the NCCI must match the length of the
specified NCCI format."REFERENCE"ATM Forum NCCI v1.0 section 2"::={ ncciIfEntry 6}ncciIfCastType OBJECT-TYPESYNTAXINTEGER{p2p (1),p2mp (2),p2pANDp2mp (3)}MAX-ACCESSread-createSTATUScurrentDESCRIPTION"Indicates if the NCCI configuration for this interface
applies to point-to-point calls only, to
point-to-multipoint calls only, or to both"::={ ncciIfEntry 7}ncciIfVpType OBJECT-TYPESYNTAXINTEGER{none (1),svp (2),spvpInitiator (3),svpANDspvpInitiator (4)}MAX-ACCESSread-createSTATUScurrent
DESCRIPTION"Indicates if the NCCI configuration for this interface
applies to svps only, to soft pvps only, to both, or to none
'svp' value applies to switched portions of a soft pvp as well
as switched vps."::={ ncciIfEntry 8}ncciIfVcType OBJECT-TYPESYNTAXINTEGER{none (1),svc (2),spvcInitiator (3),svcANDspvcInitiator (4)}
MAX-ACCESSread-createSTATUScurrentDESCRIPTION"Indicates if the NCCI configuration for this interface
applies to svcs only, to soft pvcs only, to both, or to none
'svc' value applies to switched portions of a soft pvc as well
as switched vcs."::={ ncciIfEntry 9}ncciIfRowStatus OBJECT-TYPESYNTAXRowStatusMAX-ACCESSread-createSTATUScurrentDESCRIPTION"To create, delete, activate and de-activate a NCCI
configuration for an interface."::={ ncciIfEntry 10}
-- ========================================
-- Ncci Vpl Table
-- ========================================ncciVpTable OBJECT-TYPESYNTAXSEQUENCEOF NcciVpEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The table used to manage NCCIs and their association
with a point-to-point or point-to-multipoints PVPs and
Soft PVPs in a switching system.
This table is an augmentation of atmVplTable."REFERENCE"ATM Forum NCCI v1.0"::={ ncciMIBObjects 2}ncciVpEntry OBJECT-TYPESYNTAX NcciVpEntry
MAX-ACCESSnot-accessible
STATUScurrentDESCRIPTION"Each entry in this table represents a NCCI associated with
a PVP or Soft PVP connection.
The content of this table reflects only the NCCI values
associated with VPCs. atmVplTable is specified in
ATM-MIB (RFC 2515).
This entry serves to identify the VPL on the interface."AUGMENTS{ atmVplEntry }::={ ncciVpTable 1}
NcciVpEntry ::=SEQUENCE{
ncciVpLocalType AtmNcciType,
ncciVpLocalValue AtmNcci,
ncciVpRemoteType AtmNcciType,
ncciVpRemoteValue AtmNcci
}ncciVpLocalType OBJECT-TYPESYNTAXAtmNcciTypeMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The format of the NCCI contained in the NCCI ncciVpLocalValue."REFERENCE"ATM Forum NCCI v1.0 section 2"::={ ncciVpEntry 1}ncciVpLocalValue OBJECT-TYPESYNTAXAtmNcciMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The NCCI value associated with the VPC identified by
its atmVpl. It contains the the value
- of the assigned NCCI if a new NCCI has been assigned,
- of a received NCCI if it has been forwarded,
- of a received NCCI if it has been discarded and the
atmVplConnKind for this entry is 'svcOutgoing'
- of a received NCCI if the atmVplConnKind is 'spvcTarget'
The length and type of the NCCI is determined by the
ncciVpLocalType."REFERENCE"ATM Forum NCCI v1.0 section 2"::={ ncciVpEntry 2}ncciVpRemoteType OBJECT-TYPESYNTAXAtmNcciTypeMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The format of the NCCI contained in the NCCI ncciVpRemoteValue."REFERENCE
"ATM Forum NCCI v1.0 section 2"::={ ncciVpEntry 3}ncciVpRemoteValue OBJECT-TYPESYNTAXAtmNcciMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The NCCI value associated with the VPC on the other side
of the interface.
When the atmVplConnKind for this entry is
'svcIncoming', contains the NCCI value received in the SETUP
message on the interface.
When the atmVplConnKind for this entry is
'svcOutgoing', contains the NCCI value
received in the CONNECT message on the interface.
The length and type of the NCCI is determined by the
ncciVpRemoteType."REFERENCE"ATM Forum NCCI v1.0 section 2"
::={ ncciVpEntry 4}-- ========================================
-- Ncci Vcl Table
-- ========================================ncciVcTable OBJECT-TYPESYNTAXSEQUENCEOF NcciVcEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The table used to manage NCCIs and their association
with a point-to-point or point-to-multipoints PVCs and
Soft PVCs in a switching system.
This table is an augmentation of atmVclTable."REFERENCE"ATM Forum NCCI v1.0"::={ ncciMIBObjects 3}ncciVcEntry OBJECT-TYPE
SYNTAX NcciVcEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"Each entry in this table represents a NCCI associated with
a PVC or Soft PVC connection.
The content of this table reflects only the NCCI values
associated with VCCs. atmVclTable is specified in
ATM-MIB (RFC 2515).
This entry serves to identify the VCL on the interface."AUGMENTS{ atmVclEntry }::={ ncciVcTable 1}
NcciVcEntry ::=SEQUENCE{
ncciVcLocalType AtmNcciType,
ncciVcLocalValue AtmNcci,
ncciVcRemoteType AtmNcciType,
ncciVcRemoteValue AtmNcci}ncciVcLocalType OBJECT-TYPESYNTAXAtmNcciTypeMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The format of the NCCI contained in the NCCI ncciVcLocalValue."REFERENCE"ATM Forum NCCI v1.0 section 2"::={ ncciVcEntry 1}ncciVcLocalValue OBJECT-TYPESYNTAXAtmNcciMAX-ACCESSread-onlySTATUScurrent
DESCRIPTION"The NCCI value associated with the VCC identified by
its atmVcl. It contains the value
- of the assigned NCCI if a new NCCI has been assigned,
- of a received NCCI if it has been forwarded,
- of a received NCCI if it has been discarded and the
atmVclConnKind for this entry is 'svcOutgoing'
- of a received NCCI if the atmVclConnKind is 'spvcTarget'
The length and type of the NCCI is determined by the
ncciVcLocalType."REFERENCE"ATM Forum NCCI v1.0 section 2"::={ ncciVcEntry 2}ncciVcRemoteType OBJECT-TYPESYNTAXAtmNcciTypeMAX-ACCESSread-onlySTATUScurrentDESCRIPTION
"The format of the NCCI contained in the NCCI ncciVcRemoteValue."REFERENCE"ATM Forum NCCI v1.0 section 2"::={ ncciVcEntry 3}ncciVcRemoteValue OBJECT-TYPESYNTAXAtmNcciMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The NCCI value associated with the VCC on the other side
of the interface.
When the atmVclConnKind for this entry is
'svcIncoming', contains the NCCI value received in the SETUP
message on the interface.
When the atmVclConnKind for this entry is
'svcOutgoing', contains the NCCI value
received in the CONNECT message on the interface.
The length and type of the NCCI is determined by the
ncciVcRemoteType."REFERENCE"ATM Forum NCCI v1.0 section 2"::={ ncciVcEntry 4}-- conformance informationncciMIBConformance
OBJECTIDENTIFIER::={ atmfNcciMIB 2}ncciMIBCompliances
OBJECTIDENTIFIER::={ ncciMIBConformance 1}ncciMIBGroups
OBJECTIDENTIFIER::={ ncciMIBConformance 2}-- compliance statementsncciMIBCompliance MODULE-COMPLIANCE
STATUScurrentDESCRIPTION"The compliance statement for entities which implement
the AESA-based NCCI MIB.
Groups of the AESA-based NCCI objects required for using the
NCCI extension are identified by the suffix MinGroup.
Groups of optional NCCI objects are identified by the
suffix OptionalGroup."MODULE-- this moduleMANDATORY-GROUPS{
ncciIfMinGroup,
ncciVcMinGroup
}::={ ncciMIBCompliances 1}-- units of conformancencciIfMinGroup OBJECT-GROUPOBJECTS{
ncciIfAction,
ncciIfSave,
ncciIfinConnect,
ncciIfType,
ncciIfRoot,
ncciIfCastType,
ncciIfVcType,
ncciIfRowStatus
}STATUScurrentDESCRIPTION"A collection of per interface NCCI management objects required
for managing the NCCI extension in a switching system."::={ ncciMIBGroups 1}ncciVcMinGroup OBJECT-GROUPOBJECTS{
ncciVcLocalType,
ncciVcLocalValue,
ncciVcRemoteType,
ncciVcRemoteValue
}STATUScurrentDESCRIPTION"A collection of per Vc NCCI objects required
for managing the NCCI extension in a switching system."::={ ncciMIBGroups 2}ncciIfVpOptionalGroup OBJECT-GROUPOBJECTS{
ncciIfVpType
}STATUScurrentDESCRIPTION"A collection of per interface NCCI management objects required
for managing the NCCI extension when VPs are supported
in this switching system."::={ ncciMIBGroups 3}ncciVpOptionalGroup OBJECT-GROUPOBJECTS{
ncciVpLocalType,
ncciVpLocalValue,
ncciVpRemoteType,
ncciVpRemoteValue
}STATUScurrentDESCRIPTION"A collection of per VP NCCI management objects required
for managing the NCCI extension when VPs are supported
in this switching system."::={ ncciMIBGroups 4}END